-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple ogre + OSX #5
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Follow-up on conda-forge/libignition-rendering4-feedstock#8 |
@conda-forge-admin, please rerender |
…da-forge-pinning 2021.03.23.17.55.38
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-webservice. |
@conda-forge-admin, please rerender |
…da-forge-pinning 2021.03.23.17.55.38
Hey @traversaro - note that the conda_build_config had the wrong suffix (yml instead of yaml) and thus wasn't picked up (i.e. not the macos stuff either). Could be relevant for the osx builds. |
Yes, I noticed and fixed as well in the other PRs, sorry for not highlighting it. |
On ogre 1.10 sth pulls in libarchive - I tried adding it to the host deps but still the system one is found:
I think they are exactly the same tests that fail for ogre 1.12, there with
|
Interesting, so both ogre 1.10 and 1.12 do not work correctly when running the tests during conda-build. On the other hand, as far I understand (for 1.12 from #3 (comment), for 1.10 because people actually use Gazebo on macOS) it seems that on most users setup ogre for some reason works. I wonder if this means that we should skip the test on macOS for now, open an issue to track this but for the time being enabling the macOS builds for both ogre 1.10 and 1.12 . |
Hmm. When I tried locally, I could execute the unit test fine when changing the directory to be in the same directory as the exectuable. E.g. cd test; ./UNIT_Lidar_test was running fine, while A wild guess in the dark could be that this might be fixed by setting some rpath related cmake variables. :) |
@wolfv - was that the case for both the ogre1.10 and ogre1.12 builds? |
I only tested 1.12 |
Alright, that's even better as the test error there seems "more severe". @traversaro would you be happy to look into the rpath stuff? You're probably ten times faster than what I'd be. |
I'll try. I just realized that I can actually get a test macOS machine at work, I will try to use it for this debug. |
So setting |
Two options I guess: Disabling the failing tests for now and open an issue, or digging deeper (including RPATH etc). What do you think @traversaro @wolfv? |
Quick reminder @traversaro @wolfv |
I will get access to a real mac today. I will check if a basic example is able to start, and if yes I would merge, otherwise I would wait. |
Hi @traversaro - did you have a chance to check this on a physical mac? |
Sorry, still on the backlog, but on the top of it! |
Hi! This is the friendly automated conda-forge-linting service. I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug. |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2021.05.12.18.50.42
I am finally back on it. I don't think anything that used ignition-rendering-ogre on macOS was working back in time due to gazebosim/gz-rendering#454 . However, I think we may probably have the same tests problem we have in conda-forge/libignition-rendering4-feedstock#19 (comment) . So, I think we can revive this PR, supress any test failure we may have, and then check if the tests of the fortress version work fine (we can also fix older version if there is interest, but I would start by getting the Fortress version to work). What do you think @Tobias-Fischer ? |
@conda-forge-admin, please rerender |
…a-forge-pinning 2021.10.07.13.38.58
Hi! This is the friendly automated conda-forge-linting service. I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug. |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
@conda-forge-admin, please rerender |
…a-forge-pinning 2021.10.07.13.38.58
I'd be happy for this one to be merged in. |
recipe/meta.yaml
Outdated
run: | ||
- __osx >={{ MACOSX_DEPLOYMENT_TARGET|default("10.9") }} # [osx and x86_64] | ||
- {{ pin_compatible('ogre', max_pin='x.x') }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should not be needed actually.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is true for the latest version of ogre, but note that here we link a bit old versions such as 1.10 or 1.12, the run_exports are set correctly also there?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the latest 1.10 build has it as well: https://github.com/conda-forge/ogre-feedstock/blob/5235a903689d335447e76f1397d62afd4b9b7dda/recipe/meta.yaml#L19
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, let's remove it then.
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)